Auto-update TUM fields upon calendar change
When you import a calendar with different period timespans, the software automatically recalculates resource time usage field values to match the new calendar structure.
Example scenario
You initially use a monthly calendar:
|
Period Name |
Period Start |
Period End |
|---|---|---|
|
January |
1/1/2026 12:00 AM |
2/1/2026 12:00 AM |
|
February |
2/1/2026 12:00 AM |
3/1/2026 12:00 AM |
|
March |
3/1/2026 12:00 AM |
4/1/2026 12:00 AM |
With these time usage field values (refer to Client > Resources tab):
|
Resource |
Field |
January |
February |
March |
|---|---|---|---|---|
|
922-1 |
Availability |
90% |
95% |
90% |
|
Utilisation |
87% |
90% |
84% |
|
|
Efficiency |
92% |
75% |
70% |
|
|
Rate Factor |
100% |
85% |
100% |
You then import a weekly calendar. The software recalculates the field values for each week based on the overlap with the original monthly values.
How the recalculation works
Based on the new calendar, the software recalculates the availability, utilisation, and efficiency fields for each resource.
-
Availability is weighted by the duration of each overlapping period.
-
Utilisation is weighted by (Utilisation × Availability).
-
Efficiency is weighted by (Utilisation × Availability × Efficiency).
This ensures that the new values accurately reflect the original data, proportionally distributed across the new calendar.
Resulting weekly values
|
Resource |
Field |
W1 |
W2 |
W3 |
W4 |
W5 |
W6 |
W7 |
W8 |
W9 |
W10 |
W11 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
922-1 |
Availability |
90% |
90% |
90% |
90% |
93% |
95% |
95% |
95% |
92% |
90% |
90% |
|
Utilisation |
87% |
87% |
87% |
87% |
89% |
90% |
90% |
90% |
87% |
84% |
84% |
|
|
Efficiency |
92% |
92% |
92% |
92% |
82% |
75% |
75% |
75% |
72% |
70% |
70% |
|
|
Rate Factor |
100% |
100% |
100% |
100% |
91% |
85% |
85% |
85% |
94% |
100% |
100% |